Replaces repeated `if (value) result.field = value` chains with a
single `compact()` pass from `@shopify/cli-kit/common/object`,
flattening buildResult, applyVerboseFields, buildPlan, and mapAdminShop.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Aligns with the rest of the store: namespace (e.g. store execute) which
takes the shop domain via `-s, --store` rather than a positional.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Hoists the `-s, --store` flag definition into packages/store/src/cli/flags.ts
following the themeFlags/appFlags precedent. `store auth`, `store execute`,
and `store info` now share the same flag declaration.

Side effect: the per-command verbal description ("…to authenticate against",
"…to execute against", "…to inspect") collapses into "The myshopify.com
domain of the store." — visible only in --help. The verb is redundant with
the command name.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

BP's Destinations + Organizations APIs return primaryDomain/webUrl as
full URLs with scheme ("https://shop.myshopify.com"), not bare hosts.
Strict string equality against the requested store FQDN missed every
real shop. They also return `handle: null` and a non-subdomain
`shortName` (e.g. "ACT"), so admin_url construction had nothing to work
with.

- Extract host from URL fields before comparing (new info/host.ts).
- Derive the canonical myshopify subdomain from primaryDomain/webUrl
  and overwrite destination.handle with it so admin_url is built from
  the actual shop subdomain.
- Use primaryDomain (storefront URL) for primary_url instead of
  webUrl/url (both are admin URLs ending in /admin).
- Drop the misleading `url` field from OrganizationShopFields and the
  Org GraphQL selection — it's the admin URL, not the storefront.
- Correct features.branding type from boolean to string (it's an enum
  like "SHOPIFY", not a flag).

Verified live against ariel-caplan-test: Tier 1, 2, and 3 all populate.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Keys render as "Store Type" instead of "store_type", and GraphQL enum
strings like APP_DEVELOPMENT render as "App Development". Currency
codes like USD pass through unchanged.

CLI commands take --store as a domain, so BP/Core shop IDs and the
owning-org id have no follow-on use for users of this command.
is_main_shop is a billing-contract internal that almost no user cares
about. Removed from both text and JSON output; org id is kept as an
internal-only type to drive the BP Organizations request.

Local-time output without a timezone is ambiguous when sharing output
across regions; rendering in UTC makes timestamps unambiguous regardless
of where the user is.

Drop references to "Tier", "Identity", and "Business Platform" from the
command description, section titles, and error reasons — those are
internal taxonomy that users don't recognize.

--verbose is a global "show your work" flag (more diagnostic output)
across the CLI; using it to mean "include more result fields" is a
mismatched concept. --full reads naturally as "give me the full set
of fields".

Drop the features sub-object: storefront is uniformly true, branding is
cosmetic, harmonizedSystemCode is niche cross-border tooling. Lift
shopifyPlus to a top-level `plus` boolean — it overlaps with plan.name
but is relevant enough on its own to deserve a clean signal rather than
requiring callers to regex-match plan names.

--full now adds exactly: shop_owner, timezone, setup_required, plus.

…uthed

The flag was redundant: we already know whether the store is
authenticated by the time we compose the result, so gating the Admin
fetch behind an opt-in flag just added friction without unlocking
anything. Now `store info` quietly includes shop_owner/timezone/
setup_required/plus when `store auth` exists for the store, and omits
them otherwise. The `auth_status: not authenticated` field already
serves as the discoverability hint, so we don't pollute output with
field errors for fields the user never asked for.

Replace data-source-based section names (Overview / Plan & lifecycle /
Admin details) with categories users actually think in: Store, Access,
Plan, Activity. Timezone is a store property, so it sits in Store
rather than Activity.

The --verbose flag was removed when Admin-sourced fields became
automatic for authed shops; the test still asserted on it.

knip flagged a handful of types and option interfaces that were
exported but only referenced inside their own file. Also drop the
stale --full and Tier-1/2 comments from the result envelope.

Both @Shopify/organizations and the store info plumbing were decoding
base64-encoded organization GIDs. Pull the helper into the
organizations package's models module and export it, then have
store info import it.

Returns string | undefined so each caller can decide what to do on
failure: fetchOrganizations still aborts (the id is required to
display the org); store info silently omits the id (the BP
Organizations request would have failed with a garbage id anyway).

Neither helper was specific to store info — extractHost is a generic
URL→host parser, and extractMyshopifyHandle is Shopify-domain logic
that already has neighbors in cli-kit. Move both into
@shopify/cli-kit/common/url alongside isValidURL and safeParseURL,
add direct tests, and delete the store/info/host.ts module.

extractHost now uses safeParseURL to avoid a bare try/catch.

Follow the repo convention used by other packages: queries live in
.graphql files under src/cli/api/graphql/<api>/queries/, with typed
documents generated alongside. Replaces hand-written inline query
strings and hand-typed response interfaces with the businessPlatform-
RequestDoc / businessPlatformOrganizationsRequestDoc / adminRequestDoc
typed-document variants.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

The schema files are sourced from external repos at codegen time (mirroring how packages/app and packages/organizations work) and shouldn't be tracked.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Align `store info` to the store-management project brief's dev-store
contract, sourcing every field from the Business Platform: the result is
now camelCase (id, displayName, subdomain, organizationId,
organizationName, storeOwner{name,email}, type, featurePreview,
adminUrl) and `id` is a `gid://shopify/Shop/<id>` GID.

Owner and feature preview come from BP Organizations
(Shop.ownerDetails, Shop.developerPreviewHandle), so the command no
longer needs Admin access. This lets us drop the `store auth`/Admin data
tier entirely — its service modules, GraphQL query and codegen project,
and the per-field error plumbing — along with the timezone, setup
status, and Plus-subscription fields it backed.

`plan` is intentionally deferred (see the TODO notes) pending the
internal-name -> public-handle mapping decision.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Surface the store's plan as a public handle (basic | grow | advanced |
plus) in both the text and `--json` output, sourced from BP
`Shop.planName`.

The raw plan names BP returns are Shopify-internal and differ from the
marketing names (e.g. `professional` is Grow, `unlimited` is Advanced),
so they're mapped through a hardcoded 1:1 table in `plan.ts`. Both the
internal name and the public handle are accepted as keys since the exact
form BP returns isn't pinned down by the schema. Plans not in the table
are treated as unrecognized and omitted from the output.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

The BP destinations query pulled name/handle/shortName/isAppDevelopment to
back display-name/type/admin-url fallbacks, but the contract sources those
fields from the Organizations call. Trim the destinations query to publicId
(for the owning-org lookup) plus the primaryDomain/webUrl used to match the
store, and derive admin_url from the validated `--store` domain. The shop
GID is built locally from the numeric ShopifyShopID, so nothing is fetched
purely to format the `id`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>